[6.x] [config] logging.useUTC -> logging.timezone (#21561)#22697
Merged
jbudz merged 1 commit intoelastic:6.xfrom Sep 5, 2018
Merged
[6.x] [config] logging.useUTC -> logging.timezone (#21561)#22697jbudz merged 1 commit intoelastic:6.xfrom
jbudz merged 1 commit intoelastic:6.xfrom
Conversation
* [config] logging.useUTC -> logging.timezone * docs * [env] exit if starting as root * fix import path * add link and timezone example * Revert "[env] exit if starting as root" This reverts commit f6e9090833a5180fe360a9ff54543c37c0ca3a58.
Member
|
Not sure what happened to the description - might want to give it an update. |
Contributor
💚 Build Succeeded |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This deprecates logging.useUTC and replaces it with logging.timezone. The default timezone is still UTC. To use a local timezone set logging.timezone: false We'll have a followup PR targeting 7.0 to remove the deprecation notice and default to a local timezone (and remove the optional 'false' schema).
Explicit timezones help in situations such as docker containers where the system timezone isn't necessarily setup to be your timezone.
Closes #11038.